home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000011_kane@sonata.cc.purdue.edu_Tue Sep 14 17:27 MDT 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
4KB
Received: from yvax.byu.edu by maine.et.byu.edu; Tue, 14 Sep 93 17:27:58 -0600
Return-Path: <kane@sonata.cc.purdue.edu>
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2Y35FWVY891WHHO@yvax.byu.edu>; Tue, 14 Sep 1993 17:25:55 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2Y35D3LTS934RKD@yvax.byu.edu>; Tue, 14 Sep 1993 17:25:51 MDT
Received: from yvax.byu.edu by alaska.et.byu.edu; Tue, 14 Sep 93 17:27:34 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2Y350YE1S934PJX@yvax.byu.edu>; Tue, 14 Sep 1993 17:25:35 MDT
Received: from sonata.cc.purdue.edu by yvax.byu.edu (PMDF V4.2-13 #4169) id
<01H2Y34X4OHS934RKC@yvax.byu.edu>; Tue, 14 Sep 1993 17:25:30 MDT
Received: from prelude.cc.purdue.edu by sonata.cc.purdue.edu (5.61/Purdue_CC)
id AA21267; Tue, 14 Sep 93 18:25:19 -0500
Received: by prelude.cc.purdue.edu (NX5.67d/NX3.0X) id AA02363; Tue,
14 Sep 93 18:25:23 -0500
Received: by NeXT.Mailer (1.95)
Received: by NeXT Mailer (1.95)
Date: Tue, 14 Sep 1993 18:25:23 -0500
From: kane@sonata.cc.purdue.edu
Subject: Re: External files & allowable contributions
To: misckit@byu.edu
Message-Id: <9309142325.AA21267@sonata.cc.purdue.edu>
Content-Transfer-Encoding: 7BIT
Status: R
yackd@alaska.et.byu.edu (Don Yacktman) writes:
> What I was thinking of with this suggestions is something along
> the lines of how NEXTSTEP shares .nibs among apps. There are
> actual .nibs for things like the open/save/alert/font panels in,
> I believe, /usr/lib/NextStep (the path is something like that).
> Putting them in /LocalLibrary/MiscKit would mirror this fairly
> closely.
[and there has been other discussion of /LocalLibrary heirarchies,
and related, which I'll not quote.....]
Setting up an analog to /usr/lib/NextStep/Resources, or some
related analog (/LocalLibrary/*, etc), to achieve some sharing,
and having Installer (a reasonable method) install the files
in these sort of locations is a nice idea, if you (as developer)
have (or Joe User has) the 'power' to write files into these
areas. Joe User (and developers) on a LAN administered by the
organization they're part of probably doesn't have write
permission into these areas. Expecting that sysadmins would be
happy to change this, or would be accomodating to install
things for users, is expecting *way* too much. Having your own
NeXT on your desk (or being a sysadmin) is swell, but there will
be a good chunk of users (users in education and corporate come
to mind) that'd lose on such a strategy.
Someone else wrote (sorry, I don't have the original article to
attribute this):
> As for the problem of auxiliary files for MiscKit, I'm in favor of
> something like Don proposed. However, the proper place for bundles
> is /LocalApps or ~/Apps, not the *Library directories (NeXT says
> this). Depending on the naming convention for the kit, it would
> probably be wise to have one bundle per prefix or something.
Does the "bundles belong in *Apps" approach apply to all bundles,
or just WM inspector bundles or services? I'm skeptical of the
former (and I can't locate anything that says this), but the later
two cases are documented.
Preferences bundles have to be in ~/Library/Preferences,
/LocalLibrary/Preferences, /NextLibrary/Preferences, or
/NextApps/Preferences.app. If there is a UI-type convention to
put all bundles in *Apps, NeXT has broken it itself. (Wait a minute.
What am I saying?! Why do I sound surprised?!! :-)) But somehow,
it just doesn't make sense.
Christopher Kane
kane@cs.purdue.edu